| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_1_Record_Management |
| Title | CPS.1 Record Management (Header) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Manage the patient record including all patient demographics, identifiers and other information to support the provision of care. |
| Purpose | Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage the patient record including all patient demographics, identifiers and other information to support the provision of care.
Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications.
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMHeader"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage the patient record including all patient demographics, identifiers and other information to support the provision of care.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications.</p>\n</div></span>\n \n\n \n\n \n <table id=\"statements\" class=\"grid dict\">\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.1",
"version" : "2.1.0",
"name" : "CPS_1_Record_Management",
"title" : "CPS.1 Record Management (Header)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage the patient record including all patient demographics, identifiers and other information to support the provision of care.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications."
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.